Add custom response parser option and enhance binary data handling - #103
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces support for a custom
parseroption in the request configuration, allowing users to fully control how HTTP responses are parsed. It also refines the default binary response parsing behavior to useArrayBufferfor a broader set of binary content types, and updates the response wrapper to provide consistent, idempotent methods for accessing parsed data. Documentation and tests have been updated to reflect these enhancements.✨ Features & Improvements
parseroption to config (both global and per-request) for custom response parsing.response.datais nowArrayBufferfor binary content types..blob()and.bytes()methods create and returnBlob/Uint8Arrayon demand.parseroption with XML/CSV examples and fallback parsing order.